-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mavenview #273
Mavenview #273
Conversation
…e unit test suite patches for maven build
…e unit test suite patches for maven build
Oh man, thank you SO much for the maven plugin fix! So would this replace the "build.sh pom" command entirely? |
It does, except it doesn't implement the maven-gpg-plugin, but I was not sure if anyone actually used this. Obviously it would be easy to add. Two Quick things:
Let me know if you need me to make either of those mods to my fork for the pull request. Cheers. //Nicholas |
And it also occurred to me that the maven-view.sh execution currently prompts the user to continue. This should probably have an override for automated build environments (like Jenkins et. al.) so the code can be cloned, mavenized, built and tested automatically. Let me know if you want this to go in the fork. |
Hi Nick, could you take a look at #303? I tried it against next and it worked well to create the sym links for IDEs and run the unit tests with the plugins under Maven. Will it work for the FatJar compilation? |
Will do. Need 24 hrs.
|
Chris; Have not tried it yet, but it looks good. //Nicholas |
This is all merged into 3.0 right? So we can close this PR? |
Yeah we have Maven in 3.0 so we'll close this one for now. Thanks! |
This is a modified implementation of this mavenization proposal https://groups.google.com/forum/#!topic/opentsdb/lQQgU6hf6rU.
The basics are:
Running unit tests in the mavenview created a couple of issues, addressed with the following changes in src/test:
Currently 18 out of 1362 unit tests are failing, mostly because mygnuplot.sh is not in the CLASSPATH. I propose that this be addressed as part of making the FatJar executable ( issue #272 ).
In two cases, the @PowerMockIgnore annotation had to be updated to add a new package.